Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error reporting is sometimes vague #102

Open
cvrebert opened this issue Feb 3, 2014 · 11 comments
Open

Error reporting is sometimes vague #102

cvrebert opened this issue Feb 3, 2014 · 11 comments

Comments

@cvrebert
Copy link
Contributor

cvrebert commented Feb 3, 2014

Example: https://travis-ci.org/twbs/bootstrap/jobs/18113236

Tested http://127.0.0.1:3000/js/tests/index.html
Platform: undefined
>> Test Error
Url undefined

(I had to use process of elimination to determine that this error was from OS X Chrome.)

@Jonahss
Copy link
Collaborator

Jonahss commented Feb 3, 2014

Hmm. Thanks.
No matter what fails we should always have the test params available, so should be an easy fix. It's on my list.

@tofumatt
Copy link

Any news on this? I've been bit by this in my Sauce Labs localForage branch. I'm looking to run tests on Sauce Labs, but the errors (that might be config-related, but I can't tell) aren't helpful at all.

@Jonahss
Copy link
Collaborator

Jonahss commented May 19, 2014

Yup, I've got the Sauce Api reporting job errors a little better now. I'll see how to add better error reporting on tasks.

You're just asking for better reporting through the terminal output?

@tofumatt
Copy link

Yeah, that’d be great. Right now I get errors like this, and they’re hard to debug (especially on Travis). It’d be great to get more info, at least as an option.

https://www.dropbox.com/s/itiz1cktm6ow0e6/Screenshot%202014-05-20%2011.56.05.png

@flowersinthesand
Copy link
Contributor

Any update on this? In my case, 24/32 tests showed that log and in tests page they are marked as 'Finished'. More than that, what's the reason?

@gvas
Copy link
Contributor

gvas commented May 31, 2014

This Finished status may also indicate that the test result exceeds 64KB, see #123. Does the error still persist if you remove some of your tests?
Anyway, I'm currently working on a fix for this bug, will create a pull request in a couple of hours.

@flowersinthesand
Copy link
Contributor

Thanks for response. How can I check the test result's size? I'll try it out by removing some tests.

@gvas
Copy link
Contributor

gvas commented May 31, 2014

Log into Sauce Labs then you can access the job's log file in the url https://saucelabs.com/jobs/ <jobid>/log.json. It consists of an array of log entries, you have to select the one in which your tests' descriptions appear. Then you have to check the size of the entry's result property.

@flowersinthesand
Copy link
Contributor

I tried by removing some tests but got no better. So 64KB applies to each entry's result property not log.json? My log.json's size is about 23KB or so. Hmm...

@flowersinthesand
Copy link
Contributor

Thanks @gvas. With 8.0.1 grouping tests per browser It seems that the issue is solved.

@flowersinthesand
Copy link
Contributor

Well, without grouping, the issue still occurs but the log in the first content doesn't appear. Anyway I'll group tests.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants