Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
Martin Page
@doomedramen
@mvdbeek thank you, I will look into upgrading the server
If you happen to know where to check the line ends option it would be good so I can confirm if its enabled or not
Nicola Soranzo
@nsoranzo
Actually packages from the r channel are also in defaults, not conda-forge
John Chilton
@jmchilton
What do we think about just ignoring the error code on the Selenium tests - so they always come back green. That way people reviewing client changes could still go in and look at the results manually but a random failure or two on non-client code changing PRs don't fail the whole PR. Other ideas I'm thinking about include stepping back to requesting a review from Jenkins in order for one to launch and partitioning the selenium suite into more, smaller jobs that run faster and could be re-run on errors more quickly.
Dave B.
@davebx
for those who are only on irc, the rest was "partitioning the selenium suite into more, smaller jobs that run faster and could be re-run on errors more quickly."
Dannon
@dannon
Heh, just booted up my gitter tab to read the rest.
Dave B.
@davebx
silly 20th century 512-character limit
Dannon
@dannon
It'd definitely be good to cut down on the noise, and load, but I worry that the sort of 'allowed failures' will just end in stuff staying broken.
That, or maybe worse, not noticing when things do break unrelated features (like the tool driven tours, or something, that you might not think to check)
Dave B.
@davebx
yeah, we had that issue when I joined the team, with buildbot constantly red and nobody willing to put in the hours/days/weeks to fix the tests
Dannon
@dannon
^ exactly.
Dave B.
@davebx
(it ended up being a few days, if memory serves)
Dannon
@dannon
Is it just completely random tests you're seeing failing, or can we keep marking stuff with the flaky-fail notation until we make it more robust, while allowing robust tests to continue to be useful?
John Chilton
@jmchilton
It is a complex mix of the two - it used to be that there were a few tests that would fail at 10% frequency and then random tests would fail at like 1% - but there is now this problem of the timeouts which I haven't gotten my head around yet but we cannot fix those with flakey annotations. The other complexity is the transient failures correspond to actual Galaxy bugs in some cases (galaxyproject/galaxy#5692 and https://github.com/galaxyproject/galaxy/issues/3782).
Dannon
@dannon
Seems to me the decision hinges on whether or not we can sort out the timeouts problem.
If we can fix the timeouts, then we should continue to let things fail (and show the failures), at least somewhat predictably.
John Chilton
@jmchilton
Alright - thanks for the input @dannon. I'll see what I can do.
Dannon
@dannon
Sure thing, let me know if I can help.
Martin Cech
@martenson
@wookoouk hey Martin, could you please repeat your issue? I got kinda lost trying to reconstruct it from past gitter messages.
Robert Leach
@hepcat72
One of our users is complaining that her runs of fastq_paired_end_interlacer is getting killed because it's exceeding its allocated memory. Lance usually handles this stuff and I'm filling in. Is there a way to increase the memory allocation in the galaxy admin settings?
Nate Coraor
@natefoo
@hepcat72: unfortunately no, it's managed via job_conf.xml
Robert Leach
@hepcat72
Ok @natefoo. Thanks for the quick response.
I'm looking at job_conf.xml, but there doesn't seem to be an entry for the tool. Is it as simple as copying some default entry and tweaking the momory? Is there a doc that will teach me how to do this?
galaxybot
@galaxybot
[mrscribe] Title: Galaxy Job Configuration Galaxy Project documentation (at docs.galaxyproject.org)
Robert Leach
@hepcat72
Thanks @nsoranzo !
Nate Coraor
@natefoo
if there's no entry for the tool then it's probably using a default, although if you have dynamic destinations defined then it could be set in one of those rules
Steven Weaver
@stevenweaver
Hey guys, just wanted to say that I’m impressed by the .travis.yml build script for tools-iuc and extensive galaxyproject documentation. :+1:
Peter Cock
@peterjc
Anyone here using Kraken and/or Kaiju? I've started work on defining Galaxy datatypes for their databases - see galaxyproject/galaxy#5704 - feedback welcome. Thanks!
galaxybot
@galaxybot
[mrscribe] Title: Define kaiju_db and kraken_db as compound datatypes [WIP] by peterjc · Pull Request #5704 · galaxyproject/galaxy · GitHub (at github.com)
Robert Leach
@hepcat72
So I believe I have made the necessary addition to job_conf.xml. Lance is the one who always restarts galaxy. I've done it on my own instance on my machine, but I don't know what the risks are of me doing it on our production server. Is there anything special someone could do other than running run.sh - like are there special options or something someone might always do? Do I need to be concerned about what user is running run.sh?
Nate Coraor
@natefoo
it's probably not using run.sh
Robert Leach
@hepcat72
Ah
OK
Nate Coraor
@natefoo
try using pstree to see what's running galaxy.
Robert Leach
@hepcat72
What am I looking for in the output? Thanks for the hand-holding, BTW ;)
python?
Nate Coraor
@natefoo
yeah it'll probably be python, or uwsgi. the -a option to pstree is useful
Robert Leach
@hepcat72
Wait, Lance just logged into Slack. I think I'll have it from here
Nicola Soranzo
@nsoranzo
You can also look for galaxy.ini probably
Nate Coraor
@natefoo
galaxybot
@galaxybot
[mrscribe] Title: galaxy/sniff.py at 8366d2b5fa32c5697306139426d85df86dac0782 · galaxyproject/galaxy · GitHub (at github.com)
Micropathology
@Micropathology
@mvdbeek I have updated galaxy and conda, now I still get issue Fatal error: Exit code 1 ()
Error: Unspecified error with Unicycler dependencies
Micropathology
@Micropathology
I have run some of the other other newly installed tools such a prokka and now i get
atal error: Exit code 2 ()
Can't locate XML/Simple.pm in @INC (you may need to install the XML::Simple module) (@INC contains: /mnt/galaxy/tool_dependencies/_conda/envs/__prokka@1.12/lib/site_perl/5.26.0/x86_64-linux-thread-multi /mnt/galaxy/tool_dependencies/_conda/envs/__prokka@1.12/lib/site_perl/5.26.0 /mnt/galaxy/tool_dependencies/_conda/envs/__prokka@1.12/lib/5.26.0/x86_64-linux-thread-multi /mnt/galaxy/tool_dependencies/_conda/envs/__prokka@1.12/lib/5.26.0 .) at /mnt/galaxy/tool_dependencies/_conda/envs/__prokka@1.12/bin/prokka line 25.
BEGIN failed--compilation aborted at /mnt/galaxy/tool_dependencies/_conda/envs/__prokka@1.12/bin/prokka line 25.
so there are some changes but still problems
John Chilton
@jmchilton
Jenkins is testing a bunch of random old already merged PRs today - for apparent reason :(
Dannon
@dannon
I thought I configured cancel-on-merge for at least some stuff a while bacfk
Or maybe it was just cancel on branch push, to interrupt and restart? I dunno.
John Chilton
@jmchilton
Its not for PRs merged today - they were merged a while ago I think. I'll see if I can find a pattern - probably just a bug in Jenkins