-
Notifications
You must be signed in to change notification settings - Fork 5
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
Green on our test suite (corner 3) #138
Comments
Setting up c2/3.pondersource.net for testing with the CEF Digital AS4 testbed |
|
Ran https://edelconf.westeurope.cloudapp.azure.com:9001/viewJob?id=9284&showHistory=true and saw this on c2:
|
I can do that with the logger |
|
https://edelconf.westeurope.cloudapp.azure.com:9001/jobQueue now makes it to: |
Line 45 of https://edelconf.westeurope.cloudapp.azure.com:9001/viewTestCase?id=46&showJobs=true suggests that it's waiting for the message to hit the AS4 interceptor. |
Working on this in the |
|
hm, seems to be fixed after a restart:
|
It seems the logger is stripping newlines. |
|
next step: send to the interceptor |
next error:
sending sample invoice for now to work around this. |
Next: |
Hm, that leads to a 500 error in the interceptor, not a 400. |
when trying the Java->PHP demo in the dev branch, now seeing:
|
That's fixed and I merged the dev branch into main. But state of this is still that the interceptor is rejecting our messages with either a 400 or a 500 response code. Let's look at it together next week! |
Picking this back up now. Will try what happens when I send c2 -> c3 directly |
I'm resizing c2 because it seems to be getting stuck on |
OK, now set up |
And |
The main problem seems to be that after a failed api call to nc1.docker, c2 becomes unreachable due to high load average |
|
On c3 this returns instantly, on c2 it hangs. |
I'm going to try passing the testbed tests with the re-signing-gateway. |
On c2:
From laptop:
|
OK, finally, after 4 hours, looks like I'm no longer stuck in the mud with this. \o/
|
Fixed SPDX headers 653d093 |
Next:
|
|
I can try to improve my message to the interceptor, but if it's just responding with 500s I may have to switch to our own test suite involving Phase4 + PeppolNext |
This is too hard and too time-consuming. We'll leave it for now, and then use our own test suite to pitch Phase4 and PeppolNext against each other. |
No description provided.
The text was updated successfully, but these errors were encountered: