Pin mujoco-py to fix gcc error

[yeukfu]

The latest mujoco-py is broken because of gcc related bug. Currently we just pin its version to 2.0.2.8. This should close #1989.

[codecov]

Codecov Report

Merging #1996 into master will decrease coverage by 0.00%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #1996      +/-   ##
==========================================
- Coverage   93.55%   93.54%   -0.01%     
==========================================
  Files         190      190              
  Lines       10165    10165              
  Branches     1266     1266              
==========================================
- Hits         9510     9509       -1     
+ Misses        425      424       -1     
- Partials      230      232       +2     

Impacted Files	Coverage Δ
...e/np/exploration_policies/epsilon_greedy_policy.py	96.42% <0.00%> (-3.58%)	⬇️
src/garage/np/_functions.py	89.34% <0.00%> (-1.64%)	⬇️
src/garage/sampler/multiprocessing_sampler.py	91.94% <0.00%> (+1.34%)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update c621a56...da7ebbb. Read the comment docs.

[gitanshu]

I hadn't tried changing mujoco-py versions because there are successful runs with 2.0.2.13:
https://github.com/rlworkgroup/garage/runs/1047294065?check_suite_focus=true#step:6:2680
https://travis-ci.com/github/rlworkgroup/garage/jobs/379169587#L5022

This started breaking 3 days ago but I don't see any new mujoco-py or conda releases in that period.

Anyway, I tried with different versions and somehow 2.0.2.8 works fine and so does 2.0.2.10 but 2.0.2.9 doesn't. Didn't find anything in the recent commits that would break stuff: https://github.com/openai/mujoco-py/commits/master

[yeukfu]

I hadn't tried changing mujoco-py versions because there are successful runs with 2.0.2.13:
https://github.com/rlworkgroup/garage/runs/1047294065?check_suite_focus=true#step:6:2680
https://travis-ci.com/github/rlworkgroup/garage/jobs/379169587#L5022

This started breaking 3 days ago but I don't see any new mujoco-py or conda releases in that period.

Anyway, I tried with different versions and somehow 2.0.2.8 works fine and so does 2.0.2.10 but 2.0.2.9 doesn't. Didn't find anything in the recent commits that would break stuff: https://github.com/openai/mujoco-py/commits/master

Yes, both conda and mujoco-py don't have any releases. I think this problem may be caused by some packages that mujoco-py relies on.

[ryanjulian]

@Mergifyio backport release-2020.06

[mergify]

Command backport release-2020.06: failure

No backport have been created

• Backport to branch release-2020.06 failed

Cherry-pick of a4d689a has failed:

On branch mergify/bp/release-2020.06/pr-1996
Your branch is up to date with 'origin/release-2020.06'.

You are currently cherry-picking commit a4d689a4.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Unmerged paths:
  (use "git add <file>..." to mark resolution)

	both modified:   setup.py

no changes added to commit (use "git add" and/or "git commit -a")