1113
results for "fail"
-
and when you would use that token in a client (e.g. indigenous desktop) and want to try to connect with Aperture, it will fail because the 'me' will be different in Aperture
swentel
at
2020-06-15 18:49
-
and it's usually verifying that their site can receive them, insuring that their site is sending them and having a way to retry them when they fail
jacky
at
2020-06-15 10:06
-
oops scroll state fail
[tantek]
at
2020-06-09 06:19
-
yeah, for this specific thing the testing needs to be application-specific. I guess random input/fuzzying could catch it - i.e. validating that whatever is done to the untrusted requests they either fail or produce a known-good result
sknebel
at
2020-06-01 01:22
-
I have been able to run PHP 7.3 side-by-side where the code in docker would fail, but the code on my laptop succeeded *shrug*
Zegnat
at
2020-05-30 16:56
-
I mean that big picture it is random why those specific tests fail. There are way more tests that have to handle HTML output, I think
Zegnat
at
2020-05-27 20:10
-
Having some random cases out of almost 400 test assertions in the mf2 parser fail is not really helpful in debugging ;)
Zegnat
at
2020-05-27 20:09
-
done some shopping. Zegnat, we know the exact behaviour that is telling the tests to fail. It's the solution. TBH, I'm partially happy it was the backport / trusty thing. It's 3 LTS releases ago, so I think just attempting to bump to xenial or bionic using
[LewisCowles]
at
2020-05-27 17:47
-
Zegnat, if you remove vendor/ and run "composer update" and then run the tests, do they fail?
cweiske
at
2020-05-27 13:33
-
all the non-mastermind builds fail
cweiske
at
2020-05-27 10:38
Sort by:
Filter results by:
Tag
Query took 0s.
Search tips
- Exclusion
- +foo -bar
- Logical OR
- foo OR bar
- Exact phrase
- "foo bar"
- Partial words
- foo*
- Particular fields only
- title:foo
- domain:example.org
- nick:somebody
- after:2016-11-23
- before:2016-11-23
- date:2016-11-23